Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Best practice for fault-tolerant redis with kuberay #2684

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

spencer-p
Copy link
Contributor

Why are these changes needed?

Addresses #2582

Related issue number

Closes #2582

Checks

  • No code change, no tests

Copy link
Member

@kevin85421 kevin85421 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Currently, we add the KubeRay documentation to the Ray repository so that it will automatically appear on the Ray website at https://docs.ray.io/en/latest/cluster/kubernetes/user-guides.html. Would you mind opening a PR to the Ray repository for the documentation and leaving this PR only for the YAML?

@kevin85421
Copy link
Member

Then, you can cc @rueian and me to review. Thanks!

@kevin85421 kevin85421 self-assigned this Dec 27, 2024
@rueian
Copy link
Contributor

rueian commented Dec 28, 2024

Hi @spencer-p, LGTM mostly. Thanks for the nice doc.

@spencer-p
Copy link
Contributor Author

Would you mind opening a PR to the Ray repository for the documentation and leaving this PR only for the YAML?

Of course. I had figured that would be the next step. To be clear we want to omit this from the best-practice dir in this repo entirely?

- Suggest disabling AOF on gcsfuse, s3
- Update redis version
- Don't provide a default storageClass
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Doc] Best practice to setup Redis for GCS FT
3 participants